Automate

Dependency Breakers

Automate

Automate repetitive support tasks to reduce dependencies.

Purpose

Consider automating repetitive support tasks whenever possible, but ensure appropriate controls are in place to maintain safety and quality. Examples of automation that can significantly reduce dependencies include implementing continuous integration and deployment (CI/CD) pipelines or automating routine support tasks. Automating these tasks saves time and reduces the risk of errors that can occur during manual processes. Automation boosts efficiency and allows your teams to focus on more value-added activities.

Notes

Dependencies are not necessarily bad. Actually, there are many good reasons for people to depend on each other. But you have a problem when those dependencies result in value that is not able to flow.

Rules / Constraints

  • We have not yet defined any rules or constraints.

Attend
Automate
Block
Contain
Coordinate
Decouple
Flag
Formalize
Measure
Prioritize
Redesign
Reteam
Rotate
Self-service
Standardize
Swarm
Throttle
Toggle
Visualize
Volunteer
Featured
Breaking Bad Dependencies (Not Good Ones)
Breaking Bad Dependencies (Not Good Ones)

The idea of end-to-end responsibility is that nothing is blocked in this value stream. But autonomy is an illusion, and it’s impossible to break all dependencies. The problem is that many dependencies are not valuable.

“We have broken the cycle of dependency. People have found out they're better off working.”

(Source: John Engler)